-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Micro-services deployment #882
Conversation
f7001a6
to
1e1df6f
Compare
0311f67
to
daa6e85
Compare
Rebase on 85f764d. |
bf388a1
to
1f94ec1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is pretty cool.
I'm however wondering if this is not premature optimization to split the package files at this time.
It would probably be more secure for coherency, in a first time, to install the whole package in the inginious-base container and make the other containers just run the appropriate things. That'll probably not used more space (even though it's only a few megabytes). Currently, it breaks the version number footer, which is a bit sad.
This package split could be performed in a second time, not only for a container deployment.
We can also discuss if it's worth putting those files in this particular repo as the containerfiles could be relying on pip installs. It would probably be better to maintain and be more self-documenting for sysadmins to provide docker compose files that actually perform the same operations as would be necessary for manual install method.
eb6ab61
to
ac33aef
Compare
Rebase on 61ead04. |
cbb0316
to
b34e3e3
Compare
Suggested changes by @anthonygego Co-authored-by: Anthony Gégo <[email protected]>
- Add .env file with defaults values for REGISTRY and VERSION variables - Fix "docker compose" syntax for modern deployements
b34e3e3
to
861d608
Compare
Rebase on 80e367a |
LGTM. I'll squash all the commits as they are a lot and are essentially additions |
🥳 |
* Add backend service * Add agent-docker service * Add agent-mcq service * Add mongo-db container * Layered services images * Add frontend service * [deploy] From Ubuntu to Rocky8 * [deploy] Update README * [deploy] Add initial MongoDB setup * [deploy] Update INGInious stack doc * [deploy] Rebase and update documentation * [deploy] Revert setup sub-division * [deploy] Add core containers build to CI * Use code escape in documentation Suggested changes by @anthonygego Co-authored-by: Anthony Gégo <[email protected]> * [deploy/compose] Build base image in stack deploy * [deploy] Update doc about core containers build * [deploy/base] Document the containerfile * [deploy] Update review comments - Add .env file with defaults values for REGISTRY and VERSION variables - Fix "docker compose" syntax for modern deployements --------- Co-authored-by: Anthony Gégo <[email protected]>
* Add backend service * Add agent-docker service * Add agent-mcq service * Add mongo-db container * Layered services images * Add frontend service * [deploy] From Ubuntu to Rocky8 * [deploy] Update README * [deploy] Add initial MongoDB setup * [deploy] Update INGInious stack doc * [deploy] Rebase and update documentation * [deploy] Revert setup sub-division * [deploy] Add core containers build to CI * Use code escape in documentation Suggested changes by @anthonygego Co-authored-by: Anthony Gégo <[email protected]> * [deploy/compose] Build base image in stack deploy * [deploy] Update doc about core containers build * [deploy/base] Document the containerfile * [deploy] Update review comments - Add .env file with defaults values for REGISTRY and VERSION variables - Fix "docker compose" syntax for modern deployements --------- Co-authored-by: Anthony Gégo <[email protected]>
This PR implements the feature #875.
TODO
Define a structure for the Containerfiles and setup files?[ ] Template for setup file rather than hardcoding (since only the dependencies change).[ ] setup.py template. Should be able to retrieve the current INGInious version.[ ] Multi-stage container. Stage 1 produces the setup.py file, Stage 2 is the actual container image.To implement in other PRs